System and method for facilitating cash payment transactions using a mobile device

ABSTRACT

Disclosed herein are systems and methods for facilitating transactions between a merchant-partner and an end-user. In one embodiment, a service provider: (a) stages a transaction between a merchant and a consumer; (b) creates a transaction-specific unique reference locator (URL) linked to a transaction-specific web page; and (c) sends the transaction-specific URL to the consumer&#39;s mobile device. Whereupon the consumer clicks on the transaction specific URL on their mobile device, the service provider displays a token ID on the transaction-specific web page. The token ID is linked to the staged transaction and is used to initiate data communication between a point-of-sale (POS) terminal and the service provider&#39;s processing unit. The service provider can then: receive confirmation that the consumer has presented the token ID and a payment to the POS terminal; display a transaction receipt on the transaction-specific web page; and/or notify the merchant that the consumer has provided the payment.

SUMMARY

Disclosed herein are systems and methods for facilitating transactionsbetween a merchant-partner and an end-user. More specifically, presentedherein are systems and methods for facilitating cash paymenttransactions using an end-user's mobile device. For example, in oneembodiment, the systems and methods generally call for a serviceprovider: (a) staging a transaction between a merchant and a consumer;(b) obtaining the consumer's contact information (e.g., the consumer'smobile telephone number or e-mail address); (c) creating atransaction-specific unique reference locator (URL) linked to atransaction-specific web page; and (d) sending the transaction-specificURL to the consumer. Whereupon the consumer accesses the transactionspecific web page from a mobile device, via the transaction-specificURL, the service provider: (e) displays a token ID on thetransaction-specific web page. The token ID, which is linked to thestaged transaction, is then used to initiate data communication betweena point-of-sale (POS) terminal and the service provider's processingunit. The service provider can then: (f) receive confirmation that theconsumer has presented the token ID and a payment to the POS terminal;(g) display a transaction receipt on the transaction-specific web page;and/or (h) notify the merchant that the consumer has provided thepayment.

Aspects of the present invention are particularly useful in providingmerchants (e.g., web-based or catalog-based merchants) with a means forconducting fast, easy, and secure cash transactions with consumers. Thepresent invention is also particularly useful in facilitating cashtransactions such as: loan repayments, collections, money transfers,bill payments, remote deposits, etc.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying drawings, which are incorporated herein, form part ofthe specification. Together with this written description, the drawingsfurther serve to explain the principles of, and to enable a personskilled in the relevant art(s), to make and use the claimed systems andmethods.

FIG. 1 is a high-level flow process chart illustrating the relationshipsbetween the parties that partake in the presented systems and methods.

FIG. 2 is a high-level flowchart illustrating a method for facilitatingtransactions, in accordance with one embodiment presented herein.

FIG. 3 is a flowchart illustrating one embodiment presented herein.

FIG. 4 is a schematic drawing of a computer system used to implement themethods presented.

FIG. 5 is a screenshot of an embodiment of the present invention.

FIG. 6 is another screenshot of an embodiment of the present invention.

FIG. 7 is another screenshot of an embodiment of the present invention.

FIG. 8 is another screenshot of an embodiment of the present invention.

FIG. 9 is another screenshot of an embodiment of the present invention.

FIG. 10 is another screenshot of an embodiment of the present invention.

FIG. 11 is another screenshot of an embodiment of the present invention.

FIG. 12 is another screenshot of an embodiment of the present invention.

FIG. 13 is another screenshot of an embodiment of the present invention.

FIG. 14 is another screenshot of an embodiment of the present invention.

FIG. 15 is another screenshot of an embodiment of the present invention.

FIG. 16 is another screenshot of an embodiment of the present invention.

FIG. 17 is another screenshot of an embodiment of the present invention.

FIG. 18 is another screenshot of an embodiment of the present invention.

FIG. 19 is another screenshot of an embodiment of the present invention.

FIG. 20 is another screenshot of an embodiment of the present invention.

RELATED APPLICATIONS

Except for any term definitions that conflict with the term definitionsprovided herein, the following related, co-owned, and co-pendingapplications are incorporated by reference in their entirety: U.S.patent application Ser. Nos. 13/087,271; 13/123,067; 13/175,657;13/209,291; 13/267,642; 13/298,179; and Ser. No. 13/312,835.

DETAILED DESCRIPTION

Embodiments of the present invention generally relate to systems andmethods for facilitating transactions between a merchant-partner and anend-user. For example, the present invention provides a merchant-partnerwith a means for conducting a cash transaction via a remotepoint-of-sale (POS) terminal. The present invention is particularlyuseful in facilitating transactions such as: sale/purchase agreements,loan repayments, collections, money transfers, bill payments, remotedeposits, etc. In one embodiment, a service provider and/or POS terminalserves as an intermediary between a merchant-partner and the end-user.The system allows the end-user to pay for the merchant-partner'sgoods/services/obligations in cash (or cash equivalents) at a POSterminal. The POS terminal and/or service provider then notifies themerchant-partner that the end-user has made a payment. After themerchant-partner has received a notification, validation, or otherwiseconfirmation of payment, the merchant-partner can securely complete theagreed upon transaction between the merchant-partner and the end-user.

However, in order for such system to be commercially viable, the systemsand methods presented generally include the process steps of: (a)staging a transaction between the merchant-partner and the end-user; (b)tokenizing the transaction by linking one or more transactioninstructions to one or more token IDs; (c) providing the end-user withthe one or more token IDs, wherein the end-user can then present thetoken ID and a payment to a POS terminal; (d) receiving confirmationthat the end-user has presented, to a POS terminal, the token ID and apayment in accordance with the one or more transaction instructions; (e)notifying the merchant-partner that the end-user provided the payment tothe POS terminal; and (f) settling the transaction between the POSterminal and the merchant-partner. Similar systems and methods arediscussed in more detail in the above-reference, co-owned, andco-pending applications, which have been incorporated by reference.

The present invention, expands on and further develops the systems andmethods disclosed in the above-referenced applications. Morespecifically, presented herein are systems and methods for facilitatingcash payment transactions using an end-user's mobile device. Amongstother things, the presented systems and methods provide a unique andeffective way of providing the end-user with the token ID using thefunctionality of an end-user's mobile device. For example, in oneembodiment, the systems and methods generally call for a serviceprovider: (a) staging a transaction between a merchant and a consumer;(b) obtaining the consumer's contact information (e.g., the consumer'smobile telephone number or e-mail address); (c) creating atransaction-specific unique reference locator (URL) linked to atransaction-specific web page; and (d) sending the transaction-specificURL to the consumer. When the consumer accesses the transaction specificweb page from a mobile device (e.g., via the transaction-specific URL),the service provider: (e) displays a token ID on thetransaction-specific web page. The token ID may be in the form of: abarcode, a pin number, and/or a quick response (QR) code. The token ID,which is linked to the staged transaction, is then used to initiate datacommunication between a POS terminal and the service provider'sprocessing unit. The service provider can then: (f) receive confirmationthat the consumer has presented the token ID and a payment to the POSterminal; (g) validate/verify the transaction; (h) display a transactionreceipt on the transaction-specific web page; and/or (i) notify themerchant that the consumer has provided the payment.

Before describing the invention in more detail, it is appropriate todefine certain terms and phrases. The terms “merchant” and“merchant-partner” are used interchangeably herein. It is noted that theterm “merchant” and/or “merchant-partner” is not limited to entitiesthat directly sell goods/services. For example, a merchant may be a loanservice, collections service, money transfer service, bill paymentservice, bank deposit service, credit union, etc. The terms “consumer,”“customer,” and “end-user” are used interchangeably herein, andgenerally refer to a buyer of goods/services provided by a merchant.However, it is noted that the use of the systems and methods presentedis not strictly limited to sale/purchase transactions between a sellerand a buyer. The systems and methods presented may be used to facilitatetransactions between: two or more individuals, an individual and one ormore businesses, two or more businesses, etc. The systems and methodspresented may also be used to facilitate transactions between any two ormore parties that have a pre-existing relationship or obligation(s). Theterms “point-of-sale,” “point-of-sale terminal,” “POS,” “POS terminal,”and “point-of-payment”are used interchangeably herein, and generallyrefer to the location where a payment is received from a consumer. It isalso noted that terms such as “POS” or “POS terminal” may include theactual terminal where payment is presented and received (e.g., the cashregister), or may include the POS back office, or any entity controllingone or more of the actual terminals. The terms “service provider” and“payment processor” are used interchangeably herein, and generally referto the functional unit(s) for implementing the systems and methodspresented. As used herein, a service provider may be an independent,stand-alone entity, or may be a functional sub-system of amerchant-partner and/or POS.

The following is a description of one or more embodiments of the presentinvention, with reference to FIGS. 1-20. It is to be understood that thepresent invention is not limited to the particular embodimentsdescribed. It is also to be understood that the terminology used hereinis for the purpose of describing particular embodiments only, and is notintended to be limiting, since the scope of the present invention willbe limited only by the appended claims.

FIG. 1 is a high-level flow process chart, illustrating therelationships between the parties that partake in the presented system100. In general, system 100 includes four key parties: (1) serviceprovider 102; (2) merchant-partner 104; (3) POS 106; and (4) end-user108. The dashed lines in FIG. 1 generally represent a flow ofinformation, data, or process between respective parties. In practice,the dashed lines in FIG. 1 represent user interfaces and/or applicationprogram interfaces (APIs) for the transmission of information, data,instructions, funds, etc.

As will be described further below, service provider 102 and POS 106play a central role in facilitating transactions betweenmerchant-partner 104 and end-user 108. In one embodiment, each partyserves a stand-alone function within system 100. However, in analternative embodiment, service provider 102 may be incorporated into,or be a functional unit of, merchant-partner 104 and/or POS 106.Further, merchant-partner 104 may be any type of merchant, seller, orretailer; such as an online, web-based merchant, or catalog-basedmerchant. POS 106 (and/or POS terminal) may be a local retailer (e.g.,relative to end-user 108), ATM, kiosk, or other cash-exchange terminal,intermediary, or equivalent thereof. POS 106 (and/or POS terminal) maybe disclosed/identified to the end-user 108 via one or more of thesystems described below, such as via a computer or smart phoneconnection to merchant-partner 104 or service provider 102.

In FIG. 1, process flow 120 and 122 represents an exchange betweenmerchant-partner 104 and end-user 108. In the example shown,merchant-partner 104 provides end-user 108 with a user-interface topurchase a goods/services. For example, the merchant may provide theuser with a “checkout” experience over: a web page on a merchant'swebsite; an interface on a mobile device; an interactive voice systemover a telephone network; or any interface equivalent thereof. Whileknown customer user-interfaces may provide a “checkout” experience thatallows an end-user to enter their credit card information, the systemshown in FIG. 1 provides the end-user with a checkout experience thatallows the end-user to pay for the goods/services in cash (or cashequivalents).

If the end-user selects to pay in cash, then merchant-partner 104interfaces and exchanges information with service provider 102, asrepresented by process flow 124, 126. In practice, merchant-partner 104and/or service provider 102 stages a transaction by linking a set of oneor more transaction instructions to end-user 108. The transactioninstructions may vary, but generally include instructions on whatactions (e.g., payments) need to be performed by end-user 108 in orderfor merchant-partner 104 to provide end-user 108 with the agreed upongoods/services (e.g., item 110). The transaction instructions mayinclude actions to be performed by the end-user 108, merchant-partner104, service provider 102, or any combination thereof.

Service provider 102 then “tokenizes” the staged transaction by linkingthe set of one or more transaction instructions to a token ID. (Theterms “token,” “token ID,” “unique payment identifier,” and “PID” areused interchangeably herein.) In an alternative embodiment, a singletoken ID can be linked to multiple staged transactions and/or multiplemerchant-partners. The token ID is then provided to end-user 108. Thetoken ID can be provided to the end-user 108 either directly fromservice provider 102, POS 106, or merchant-partner 104. FIGS. 5-20illustrate exemplary embodiments of how the token ID is provided toend-user 108 via an end-user mobile device.

When end-user 108 is ready to make a payment, end-user 108 presents thetoken ID to POS 106, along with an appropriate payment, as representedby process flow 128. At POS 106, the token ID serves as a means oflinking the end-user's payment to the one or more transactioninstructions. In other words, when end-user 108 presents the token IDand payment to POS 106, the token ID is used to initiate datacommunication between POS 106 and service provider 102, and therebyroute the presentment information to service provider 102, asrepresented by process flow 130, 132. Service provider 102 may thenvalidate that the presentment was in accordance with the transactioninstructions linked to the token ID. If the end-user's payment is inaccordance with the transaction instructions linked to the token ID,then service provider 102 notifies merchant-partner 104 that a paymenthas been made. Merchant-partner 104 then completes the transaction by,for example, shipping item 110 or otherwise fulfilling the transactionand/or crediting end-user's 108 account with merchant-partner 104.Service provider 102 then settles the transaction betweenmerchant-partner 104 and POS 106 by receiving the payment funds (minusany agreed upon service fees) from POS 106, and delivering the paymentfunds (minus any agreed upon service fees) to merchant-partner 104.

In an alternative embodiment, the systems and methods described hereindo not require merchant-partner 104 to provide end-user 108 with acheckout experience. There is also no requirement that the end-userprovide an intent or selection of a cash payment option. For example, inone embodiment, merchant-partner 104 provides its customers with one ormore tokens as a means for the customers to make payments. The paymentscan be made at a POS terminal, and a series of staged transactions mayproceed, without any front-end involvement by end-user 108.

FIG. 2 is a high-level flowchart illustrating a method 200 forfacilitating a transaction between a merchant-partner and an end-user,in accordance with one embodiment presented herein. More specifically,FIG. 2 is a flowchart generally illustrating the steps performed in thesystem described in FIG. 1. The method includes: (a) staging atransaction (step 201); (b) tokenizing the staged transaction (step202); (c) receiving the presentment (step 203); (d) notifying themerchant-partner that the presentment has been received (step 204); and(e) settling the transaction between the parties (step 205). Additionaldetails for steps (a)-(d) are provided in, for example, U.S. applicationSer. Nos. 13/087,271; 13/123,067; and Ser. No. 13/312,835, which areincorporated by reference herein.

FIG. 3 is a flowchart illustrating one embodiment of the presentinvention. More specifically, FIG. 3 illustrates a method 300 forproviding a consumer with the token ID created in step 202. In step 301,a transaction-specific URL is created and linked to atransaction-specific web page. In practice, the transaction-specific webpage may be maintained on the service provider's server. Additionally,step 301 typically occurs after the transaction has been staged in step201. As such, the transaction-specific URL and transaction-specific webpage can also be linked to the staged transaction and/or token ID. Instep 302, the consumer is provided with a prompt to enter their contactinformation. Such prompt can be provided on the merchant's web page, orby redirecting the consumer to the service provider's web page. Theconsumer's contact information can then be linked to the stagedtransaction. Alternatively, if the merchant is already in possession ofthe consumer's contact information, such contact information can beincluded in the staged transaction. Such contact information may includedetails such as mobile telephone numbers, e-mail addresses, instantmessaging usernames, handles, etc. In step 303, the URL is sent to theconsumer. Preferably, the consumer's contact information is used to leadthe consumer into accessing/receiving the URL on their mobile device.For example, if a staged transaction includes a consumer's e-mailaddress and mobile telephone number, the service provider's processingsystem can select to send the URL to the consumer via a short messageservice (SMS) text message to their mobile phone. Alternatively, ane-mail can be sent, but the e-mail can ask the consumer to access theURL with their mobile device (be it a mobile phone, tablet, etc.).

In step 304, the service provider's processing unit determines whetherthe consumer clicked on the URL on a mobile device. If not, the serviceprovider may continue a non-mobile implementation of the process stepsof FIG. 2, as described in the above-referenced applications. However,if the consumer has chosen to access/receive the URL on a mobile device,the service provider's processing unit receives a user-agent stringidentifying the mobile device, and assess compatibility of the mobiledevice based on the user-agent string, in step 305. By assessingcompatibility, the service provider's processing unit can adjust thetext, type, format, etc., of the information that is presented to theconsumer's mobile device. The service provider can also select/modifythe token ID based on the compatibility of the consumer's mobile device.

In step 306, the service provider's processing unit can receive ageolocation from the mobile device, and identify one or more POSterminals that may be local to the consumer, based on geolocation. Theone or more local POS terminals can then be provided to the consumer asa list (or as pin-points on a map), via the transaction-specific webpage, in step 307. Alternatively, the consumer can enter their zip code,or a preselected POS terminal, and steps 306 and 307 can be skipped. Instep 308, the service provider's processing unit determines whether theconsumer selected a POS terminal for providing the payment and/orwhether the consumer is at the POS terminal and ready to provide thepayment.

In step 309, the token ID is displayed on the transaction-specific webpage. The token ID serves as a means to initiate data communicationbetween the POS terminal and the service provider's processing unit. Thetoken ID is used by the service provider to identify the stagedtransaction, and allows the service provider to confirm whether or notthe payment is consistent with the staged transaction instructions. Forexample, in the embodiment wherein the token ID is a barcode, the POSterminal attendant scans the barcode and the POS terminal recognizesthat the barcode requires an application programming interface (API)call to the service provider's processing unit. In step 310, the serviceprovided receives confirmation from the POS terminal that the consumerhas presented the token ID and the payment to the POS terminal; i.e.,the service provider receives “presentment data” from the POS terminal.With said presentment data, the service provider can validate orotherwise verify the transaction and payment, as in step 311. Becausethe consumer is using their mobile device to display the token ID on thetransaction-specific web page, the service provider can refresh thetransaction-specific web page upon verification of the payment. Theservice provider can then display a transaction receipt on thetransaction-specific web page, in step 312.

FIGS. 5-20 are screenshots illustrating an embodiment of the presentinvention. For example, FIG. 5 shows a screenshot of a payment page fora web-based merchant (e.g., “Cute Puppies”). In FIG. 5, the consumer isgiven the option to select between multiple POS terminals to completetheir purchase transaction. FIG. 6 shows a screenshot after the consumerhas selected 7-ELEVEN™ as their POS terminal. In FIG. 6, the consumer isgiven the option to print a token ID, or have a token ID sent to theirmobile device by clicking the “Use Mobile” icon. FIG. 7 shows aprint-out of the token ID and transaction instructions if the userclicks the “Print” icon shown in FIG. 6. However, if the consumer clicksthe “Use Mobile” icon, the consumer is prompted to enter their e-mail ormobile number, as shown in the screenshot of FIG. 8. Alternatively, theconsumer's contact information may be provided by other means, such asdirectly from a database provided by the merchant, POS, and/or serviceprovider. As such, the consumer's contact information can merely be“confirmed” by the consumer.

FIG. 9 shows a mobile screenshot of an SMS text message sent to theconsumer with a transaction-specific URL, that is linked to atransaction-specific web page. The consumer, however, is given theoption of proceeding via a back-and-forth SMS text message exchange withthe service provider. For example, if the consumer's mobile device doesnot have “browser capability,” the consumer can send a return text of“No,” in which case the service provider will send SMS text messageinstructions, as shown in FIGS. 10 and 11. If the consumer clicks on thetransaction-specific URL, the process proceeds to the screen shown inFIG. 12. More specifically, FIG. 12 shows the consumer accessing thetransaction-specific web page on their mobile device (e.g., on a mobilebrowser or dedicated mobile application (or “app”)). Thetransaction-specific web page provides transaction instructions for theconsumer to complete the transaction. For example, FIG. 12 shows atransaction-specific web page with a prompt asking the user to selecttheir POS terminal, or enter a zip code or address to locate local POSterminals.

Once the consumer has selected a local POS terminal, thetransaction-specific web page is refreshed by the service provider toshow additional transaction instructions. When the consumer is at thePOS terminal, they can click on the icon “At Cashier” to proceed to POSinstructions, as shown in FIG. 14. In other words, FIG. 14 showstransaction instructions for the POS terminal. In FIG. 14, the token IDis displayed in the form of a barcode. The POS terminal can then scanthe barcode to initiate communication with the service provider. Inother words, the barcode is used as a means for initiating the transferof presentment data to the service provider.

If, however, the POS terminal attendant is unsure of how to process thetransaction, a “Need Help? Tap Here” icon is provided on thetransaction-specific web page. If the consumer or POS terminal attendantclicks on the “Need Help? Tap Here” icon, a transaction-specificinstruction set is provided by the service provider on thetransaction-specific web page. The service provider can select thetransaction-specific instruction set based on the POS terminal selectedby the consumer. FIGS. 15-19 illustrate screen shots of atransaction-specific instruction set. Each screenshot shown in FIGS.15-19 is customized to the consumer's transaction. For example, FIG. 15illustrates a terminal that matches the POS terminal. FIG. 15 alsoillustrates the transaction amount. FIGS. 16-19 then show ensuing stepsto be performed by the POS terminal attendant.

After the consumer has made a payment in accordance with the transactioninstructions, and the service provider has validated the payment, theservice provider can refresh (or otherwise update) thetransaction-specific web page to show a receipt for the transaction. Thereceipt text can provide additional instructions and/or promotions forthe consumer. The receipt text can also mimic the receipt text thatwould be (or is) otherwise provided by the POS terminal.

Additional Embodiments

In one embodiment, there is provided a computer-implemented method forfacilitating a payment for goods or services between an online merchantand a consumer. The method calls for the consumer to provide a purchaserequest on a web-based interface, and the payment for the purchaserequest at a consumer-selected point-of-sale (POS) terminal that islocal to the consumer and remote to the merchant. The purchase requestmay be received at a service provider processing unit, from themerchant's web-based interface, based on directives from a merchantserver. The purchase request may be received at a service providerprocessing unit, from the merchant's web-based interface, via anapplication programming interface (API) call from the merchant server.As would be appreciated by one of skill in the art, alternatives toweb-based interfaces are within the scope of the present invention. Inother words, any means for communicating and/or transmitting informationfrom the consumer and/or merchant may be employed; for example, anapplication (i.e., “app”) on a mobile device, an interactive voiceresponse (IVR) system, a third-party database, an operator-assistedphone call, or any other equivalent means.

The method comprises a service provider processing unit performing thesteps of: (a) receiving the purchase request from the web-basedinterface; (b) staging a transaction in a database by creating adatabase entry linking one or more transaction instructions to theconsumer; (c) creating a transaction-specific unique reference locator(URL) linked to a transaction-specific web page for displaying the oneor more transaction instructions; (d) providing the consumer with aweb-based prompt to enter their contact information; (e) receiving theconsumer's contact information and linking the contact information tothe database entry; and (f) using the provided contact information tosend the transaction-specific URL to the consumer. The consumer mayprovide their contact information in the form of an e-mail address or atelephone number. The transaction-specific URL may be sent to theconsumer in an e-mail or a short message service (SMS) text message.Whereupon the consumer clicking the transaction-specific URL on a mobiledevice, the service provider processing unit further performs the stepsof: (g) receiving a user-agent string identifying the mobile device; (h)assessing compatibility of the mobile device based on the user-agentstring; (i) receiving a geolocation from the mobile device; (j)identifying one or more POS terminals local to the consumer based ongeolocation; and (k) providing the consumer, via thetransaction-specific web page, a list of the one or more POS terminals.Whereupon the consumer's selection of a POS terminal for providing thepayment, the service provider processing unit further performing thestep of: (l) displaying a token ID on the transaction-specific web page,wherein the token ID is linked to the database entry and is used toinitiate data communication between the consumer-selected POS terminaland the service provider processing unit. The token ID may be in a formselected from the group consisting of: a barcode, a pin number, and a QRcode.

In alternative embodiments, the consumer's contact information may beobtained via an interface such as an application (i.e., “app”) on amobile device, an IVR system, a third-party database, anoperator-assisted phone call, or any other equivalent means for sharingand/or obtaining information from the consumer.

The method may further comprise: (m) providing the consumer-selected POSterminal with a communication interface such that the consumer-selectedPOS terminal can confirm that the consumer has presented the token IDand provided the payment to the POS terminal; and the service providerprocessing unit then performing the steps of: (n) receiving confirmationthat the consumer has presented the token ID and the payment to the POSterminal; (o) verifying that the payment is in accordance with the oneor more transaction instructions; and/or (p) displaying a transactionreceipt on the transaction-specific web page. The method may furtherinclude the step of (q) notifying the merchant that the consumer hasprovided the payment; and/or (r) the service provider processing unitperforming the step of selecting the form of the token ID based on thePOS terminal selected by the consumer.

In another embodiment, there is provided a method for facilitating atransaction between a merchant and a consumer, wherein the consumerprovides a payment for the transaction at a consumer-selected POSterminal. The method includes a service provider processing unitperforming the steps of: (a) receiving a service request; (b) staging atransaction in a database by creating a database entry linking one ormore transaction instructions to the consumer; (c) creating atransaction-specific URL linked to a transaction-specific web page fordisplaying the one or more transaction instructions; and (d) usingconsumer contact information to send the transaction-specific URL to theconsumer. Whereupon the consumer accesses the transaction specific webpage from a mobile device, via the transaction-specific URL, the serviceprovider processing unit further performs the steps of: (e) identifyingone or more available POS terminals; and (f) displaying the one or moreavailable POS terminals on the transaction-specific web page. Whereuponthe consumer selects a POS terminal for providing the payment, theservice provider processing unit performs the step of: (g) displaying atoken ID on the transaction-specific web page, wherein the token ID islinked to the database entry and is used to initiate data communicationbetween the consumer-selected POS terminal and the service providerprocessing unit. The token ID may be in a form selected from the groupconsisting of: a barcode, a pin number, and a QR code. The serviceprovider processing unit may further perform the steps of: (h) receivingconfirmation that the consumer has presented the token ID and thepayment to the POS terminal; (i) displaying a transaction receipt on thetransaction-specific web page; and/or (j) notifying the merchant thatthe consumer has provided the payment.

In yet another embodiment, there is provided a method for facilitating apayment between a merchant and a consumer, wherein the consumer providesthe payment at a consumer-selected POS terminal. The method comprises aservice provider processing unit performing the steps of: (a) staging atransaction in a database by creating a database entry linking one ormore transaction instructions to the consumer; (b) creating atransaction-specific URL linked to a transaction-specific web page fordisplaying the one or more transaction instructions; and (c) sending thetransaction-specific URL to the consumer via a SMS text message.Whereupon the consumer clicks the transaction-specific URL on a mobiledevice, the service provider processing unit performs the steps of: (d)displaying the one or more transaction instructions on thetransaction-specific web page; and (e) displaying a token ID on thetransaction-specific web page, wherein the token ID is linked to thedatabase entry and is used to initiate data communication between theconsumer-selected POS terminal and the service provider processing unit.The token ID may be in a form selected from the group consisting of: abarcode, a pin number, and a QR code. The method may further comprisethe service provider processing unit then performing the steps of: (f)receiving confirmation that the consumer has presented the token ID andthe payment to the POS terminal; (g) displaying a transaction receipt onthe transaction-specific web page; (h) notifying the merchant that theconsumer has provided the payment; and/or (i) selecting the form of thetoken ID based on the POS terminal selected by the consumer.

In still another embodiment, there is provided a method for facilitatinga cash payment for goods/services, wherein the consumer provides thepayment at a POS terminal. The method comprises a service providerprocessing unit performing the steps of: (a) obtaining a consumer'scontact information; (b) creating a transaction-specific URL linked to atransaction-specific web page for displaying the one or more transactioninstructions; and (c) sending the transaction-specific URL to theconsumer. Whereupon the consumer clicks the transaction-specific URL ona mobile device, the service provider processing unit performs the stepof: (d) displaying the one or more transaction instructions on thetransaction-specific web page. Whereupon the consumer indicates they arepresent at the POS terminal, the service provider processing unitperforms the step of: (e) displaying a token ID on thetransaction-specific web page, wherein the token ID is used to initiatedata communication between the POS terminal and the service providerprocessing unit. The token ID may be in a form selected from the groupconsisting of: a barcode, a pin number, and a QR code. The method mayfurther comprise the service provider processing unit then performingthe steps of: (f) receiving an amount of payment received at the POSterminal; (g) displaying a transaction receipt on thetransaction-specific web page; and/or (h) crediting a consumer account,debit card, pre-paid card, loan, or equivalent account, based on theamount of payment received at the POS terminal.

In yet another embodiment, there is provide a system and method forfacilitating a cash payment for goods or services, wherein a consumerprovides the payment at a POS terminal. The system and method include aservice provider processing unit performing the steps of: (a) creating atransaction-specific display prompt for displaying the one or moretransaction instructions; (b) sending the consumer atransaction-specific link to the transaction-specific display prompt;(c) displaying the one or more transaction instructions on thetransaction-specific display prompt; and (d) displaying a token ID onthe transaction-specific display prompt, wherein the token ID is used toinitiate data communication between the POS terminal and the serviceprovider processing unit. The system and method may further include theservice provider processing unit performing the steps of: (e) receivingan amount of payment received at the POS terminal; (f) displaying atransaction receipt on the transaction-specific display prompt; (g)crediting a consumer account, debit card, pre-paid card, or loan, basedon the amount of payment received at the POS terminal. The system andmethod presented can be implemented on a browser-based mobile prompt, oran application specific display interface.

Communication Between Parties Practicing the Present Invention.

In one embodiment, communication between the various parties andcomponents of the present invention is accomplished over a networkconsisting of electronic devices connected either physically orwirelessly, wherein digital information is transmitted from one deviceto another. Such devices (e.g., end-user devices and/or servers) mayinclude, but are not limited to: a desktop computer, a laptop computer,a handheld device or PDA, a cellular telephone, a set top box, anInternet appliance, an Internet TV system, a mobile device or tablet, orsystems equivalent thereto. Exemplary networks include a Local AreaNetwork, a Wide Area Network, an organizational intranet, the Internet,or networks equivalent thereto. The functionality and system componentsof an exemplary computer and network are further explained inconjunction with FIG. 4, below.

Computer Implementation.

In one embodiment, the invention is directed toward one or more computersystems capable of carrying out the functionality described herein. Forexample, FIG. 4 is a schematic drawing of a computer system 400 used toimplement the methods presented above. Computer system 400 includes oneor more processors, such as processor 404. The processor 404 isconnected to a communication infrastructure 406 (e.g., a communicationsbus, cross-over bar, or network). Computer system 400 can include adisplay interface 402 that forwards graphics, text, and other data fromthe communication infrastructure 406 (or from a frame buffer not shown)for display on a local or remote display unit 430.

Computer system 400 also includes a main memory 408, such as randomaccess memory (RAM), solid state device, and/or hard drive. Computersystem 400 may also include a secondary memory 410. The secondary memory410 may include, for example, a hard disk drive 412 and/or a removablestorage drive 414, representing a floppy disk drive, a magnetic tapedrive, an optical disk drive, flash memory device, universal serial bus(USB) device, etc. The removable storage drive 414 reads from and/orwrites to a removable storage unit 418. Removable storage unit 418represents a floppy disk, magnetic tape, optical disk, flash memorydevice, universal serial bus (USB) device, etc., which is read by andwritten to by removable storage drive 414. As will be appreciated, theremovable storage unit 418 includes a computer usable storage mediumhaving stored therein computer software, instructions, and/or data.

In alternative embodiments, secondary memory 410 may include othersimilar devices for allowing computer programs or other instructions tobe loaded into computer system 400. Such devices may include, forexample, a removable storage unit 422 and an interface 420. Examples ofsuch may include a program cartridge and cartridge interface (such asthat found in video game devices), a removable memory chip (such as anerasable programmable read only memory (EPROM), or programmable readonly memory (PROM)) and associated socket, and other removable storageunits 422 and interfaces 420, which allow computer software,instructions, and/or data to be transferred from the removable storageunit 422 to computer system 400.

Computer system 400 may also include a communications interface 424.Communications interface 424 allows computer software, instructions,and/or data to be transferred between computer system 400 and externaldevices. Examples of communications interface 424 may include a modem, anetwork interface (such as an Ethernet card), a communications port, aPersonal Computer Memory Card International Association (PCMCIA) slotand card, etc. Software and data transferred via communicationsinterface 424 are in the form of signals 428 which may be electronic,electromagnetic, optical or other signals capable of being received bycommunications interface 424. These signals 428 are provided tocommunications interface 424 via a communications path (e.g., channel)426. This channel 426 carries signals 428 and may be implemented usingwire or cable, fiber optics, a telephone line, a cellular link, a radiofrequency (RF) link, a wireless communication link, and othercommunications channels.

In this document, the terms “computer-readable storage medium,”“computer program medium,” and “computer usable medium” are used togenerally refer to all non-transitory computer-readable media; such asremovable storage drive 414, removable storage units 418, 422, a harddisk installed in hard disk drive 412, or equivalent computer-readablemedia with the exclusion of propagating signals. These computer programproducts provide computer software, instructions, and/or data tocomputer system 400. These computer program products also serve totransform a general purpose computer into a special purpose computerprogrammed to perform particular functions, pursuant to instructionsfrom the computer program products/software. Embodiments of the presentinvention are directed to such computer program products.

Computer programs (also referred to as computer control logic) arestored in main memory 408 and/or secondary memory 410. Computer programsmay also be received via communications interface 424. Such computerprograms, when executed, enable the computer system 400 to perform thefeatures of the present invention, as discussed herein. In particular,the computer programs, when executed, enable the processor 404 toperform the features of the presented methods. Accordingly, suchcomputer programs represent controllers of the computer system 400.Where appropriate, the processor 404, associated components, andequivalent systems and sub-systems thus serve as “means for” performingselected operations and functions. Such “means for” performing selectedoperations and functions also serve to transform a general purposecomputer into a special purpose computer programmed to perform saidselected operations and functions.

In an embodiment where the invention is implemented using software, thesoftware may be stored in a computer program product and loaded intocomputer system 400 using removable storage drive 414, interface 420,hard drive 412, communications interface 424, or equivalents thereof.The control logic (software), when executed by the processor 404, causesthe processor 404 to perform the functions and methods described herein.

In another embodiment, the methods are implemented primarily in hardwareusing, for example, hardware components such as application specificintegrated circuits (ASICs). Implementation of the hardware statemachine so as to perform the functions and methods described herein willbe apparent to persons skilled in the relevant art(s). In yet anotherembodiment, the methods are implemented using a combination of bothhardware and software.

Embodiments of the invention, including any systems and methodsdescribed herein, may also be implemented as instructions stored on amachine-readable medium, which may be read and executed by one or moreprocessors. A machine-readable medium may include any mechanism forstoring or transmitting information in a form readable by a machine(e.g., a computing device). For example, a machine-readable medium mayinclude read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; flash memory devices; andothers. Further, firmware, software, routines, instructions may bedescribed herein as performing certain actions. However, it should beappreciated that such descriptions are merely for convenience and thatsuch actions in fact result from computing devices, processors,controllers, or other devices executing firmware, software, routines,instructions, etc.

For example, in one embodiment, there is provided a computer-readablestorage medium for facilitating a payment for goods or services betweenan online merchant and a consumer. The computer-readable storage mediumincludes instructions executable by at least one processing device that,when executed, cause the processing device to: (a) receive a purchaserequest from the online merchant's web-based interface; (b) stage atransaction in a database by creating a database entry linking one ormore transaction instructions to the consumer; (c) create atransaction-specific URL linked to a transaction-specific web page fordisplaying the one or more transaction instructions; (d) provide theconsumer with a web-based prompt to enter their contact information; (e)receive the consumer's contact information and linking the contactinformation to the database entry; and (f) use the provided contactinformation to send the transaction-specific URL to the consumer.Whereupon the consumer clicks the transaction-specific URL on a mobiledevice, the computer-readable storage medium includes instructions thatcause the processing device to: (g) receive a user-agent stringidentifying the mobile device; (h) assess the compatibility of themobile device based on the user-agent string; (i) receive a geolocationfrom the mobile device; (j) identify one or more POS terminals local tothe consumer based on geolocation; and (k) provide the consumer, via thetransaction-specific web page, a list of the one or more POS terminals.Whereupon the consumer selects of a POS terminal for providing thepayment, the computer-readable storage medium includes instructions thatcause the processing device to: (l) display a token ID on thetransaction-specific web page, wherein the token ID is linked to thedatabase entry and is used to initiate data communication between theconsumer-selected POS terminal and the service provider processing unit;(m) provide the consumer-selected POS terminal with a communicationinterface such that the consumer-selected POS terminal can confirm thatthe consumer has presented the token ID and provided the payment to thePOS terminal; (n) receive confirmation that the consumer has presentedthe token ID and the payment to the POS terminal; (o) verify that thepayment is in accordance with the one or more transaction instructions;(p) display a transaction receipt on the transaction-specific web page;(q) notifying the merchant that the consumer has provided the payment;and/or (r) select the form of the token ID based on the POS terminalselected by the consumer. The token ID may be a form selected from thegroup consisting of: a barcode, a pin number, and a QR code. Thepurchase request may be received from the web-based interface based ondirectives from a merchant server. The purchase request may be receivedvia an application programming interface (API) call from a merchantserver. The consumer may provide their contact information in the formof an e-mail address or a telephone number. The transaction-specific URLmay be sent to the consumer in an e-mail or a SMS text message.

In another embodiment, there is provided a computer-readable storagemedium for facilitating a transaction between a merchant and a consumer,wherein the consumer provides a payment for the transaction at aconsumer-selected point-of-sale (POS) terminal. The computer-readablestorage medium includes instructions executable by at least oneprocessing device that, when executed, cause the processing device to:(a) receive a service request; (b) stage a transaction in a database bycreating a database entry linking one or more transaction instructionsto the consumer; (c) create a transaction-specific URL linked to atransaction-specific web page for displaying the one or more transactioninstructions; and (d) use consumer contact information to send thetransaction-specific URL to the consumer. Whereupon the consumeraccesses the transaction specific web page from a mobile device, via thetransaction-specific URL, the computer-readable storage medium includesinstructions that cause the processing device to: (e) identify one ormore available POS terminals; and (f) display the one or more availablePOS terminals on the transaction-specific web page. Whereupon theconsumer selects a POS terminal for providing the payment, thecomputer-readable storage medium includes instructions that cause theprocessing device to: (g) display a token ID on the transaction-specificweb page, wherein the token ID is linked to the database entry and isused to initiate data communication between the consumer-selected POSterminal and the service provider processing unit; (h) receiveconfirmation that the consumer has presented the token ID and thepayment to the POS terminal; (i) display a transaction receipt on thetransaction-specific web page; and/or (j) notifying the merchant thatthe consumer has provided the payment. The token ID may be in a formselected from the group consisting of: a barcode, a pin number, and a QRcode.

In another embodiment, there is provided a computer-readable storagemedium for facilitating a payment between a merchant and a consumer,wherein the consumer provides the payment at a consumer-selectedpoint-of-sale (POS) terminal. The computer-readable storage mediumincludes instructions executable by at least one processing device that,when executed, cause the processing device to: (a) stage a transactionin a database by creating a database entry linking one or moretransaction instructions to the consumer; (b) create atransaction-specific unique reference locator (URL) linked to atransaction-specific web page for displaying the one or more transactioninstructions; and (c) send the transaction-specific URL to the consumervia a short message service (SMS) text message. Whereupon the consumerclicking the transaction-specific URL on a mobile device, thecomputer-readable storage medium includes instructions that cause theprocessing device to: (d) display the one or more transactioninstructions on the transaction-specific web page; and (e) display atoken ID on the transaction-specific web page, wherein the token ID islinked to the database entry and is used to initiate data communicationbetween the consumer-selected POS terminal and the service providerprocessing unit. The computer-readable storage medium may furtherinclude instructions that cause the processing device to: (f) receiveconfirmation that the consumer has presented the token ID and thepayment to the POS terminal; (g) display a transaction receipt on thetransaction-specific web page; (h) notify the merchant that the consumerhas provided the payment; and/or (i) select the form of the token IDbased on the POS terminal selected by the consumer. The token ID may bein a form selected from the group consisting of: a barcode, a pinnumber, and a quick response (QR) code.

In still another embodiment, there is provided a computer-readablestorage medium for facilitating a cash payment by a consumer, whereinthe consumer provides the payment at a consumer-selected point-of-sale(POS) terminal. The computer-readable storage medium includesinstructions executable by at least one processing device that, whenexecuted, cause the processing device to: (a) obtain a consumer'scontact information; (b) create a transaction-specific URL linked to atransaction-specific web page for displaying the one or more transactioninstructions; (c) send the transaction-specific URL to the consumer; (d)display the one or more transaction instructions on thetransaction-specific web page; (e) display a token ID on thetransaction-specific web page, wherein the token ID is used to initiatedata communication between the POS terminal and the service providerprocessing unit; (f) receive an amount of payment received at the POSterminal; (g) display a transaction receipt on the transaction-specificweb page; and/or (h) credit a consumer account, debit card, pre-paidcard, loan, or equivalent account, based on the amount of paymentreceived at the POS terminal.

CONCLUSION

The foregoing description of the invention has been presented forpurposes of illustration and description. It is not intended to beexhaustive or to limit the invention to the precise form disclosed.Other modifications and variations may be possible in light of the aboveteachings. The embodiments were chosen and described in order to bestexplain the principles of the invention and its practical application,and to thereby enable others skilled in the art to best utilize theinvention in various embodiments and various modifications as are suitedto the particular use contemplated. It is intended that the appendedclaims be construed to include other alternative embodiments of theinvention; including equivalent structures, components, methods, andmeans.

As will be apparent to those of skill in the art upon reading thisdisclosure, each of the individual embodiments described and illustratedherein has discrete components and features which may be readilyseparated from or combined with the features of any of the other severalembodiments without departing from the scope or spirit of the presentinvention. Any recited method can be carried out in the order of eventsrecited or in any other order which is logically possible. Further, eachsystem component and/or method step presented should be considered a“means for” or “step for” performing the function described for saidsystem component and/or method step. As such, any claim languagedirected to a “means for” or “step for” performing a recited functionrefers to the system component and/or method step in the specificationthat performs the recited function, as well as equivalents thereof.

It is to be appreciated that the Detailed Description section, and notthe Summary and Abstract sections, is intended to be used to interpretthe claims. The Summary and Abstract sections may set forth one or more,but not all exemplary embodiments of the present invention ascontemplated by the inventor(s), and thus, are not intended to limit thepresent invention and the appended claims in any way.

1.-22. (canceled)
 23. A method for facilitating a payment between anonline merchant and a consumer, wherein the consumer provides a purchaserequest on a web-based interface, and wherein the consumer provides thepayment for the purchase request at a point-of-sale terminal that islocal to the consumer and remote to the merchant, the method comprising:receiving with a communications interface of a service provider systemthe purchase request made on the web-based interface; generating with aprocessor of the service provider system transaction instructions forthe purchase request; receiving with the communications interface of theservice provider system contact information for the consumer; linkingwith the processor of the service provider system the consumer's contactinformation to the transaction instructions; creating with the processorof the service provider system a transaction-specific page; updatingwith the processor of the service provider system thetransaction-specific page with instructions for the consumer on how toprovide the payment for the purchase request at the point-of-saleterminal; transmitting with the communications interface of the serviceprovider system the transaction-specific page to the consumer at theconsumer's contact information and causing the web-based interface todisplay the transaction-specific page; generating with the processor ofthe service provider system a token ID; linking with the processor ofthe service provider system the token ID to the transactioninstructions; updating with the processor of the service provider systemthe transaction-specific page to display the token ID; receiving withthe communications interface of the service provider system confirmationthat the consumer presented the token ID and the payment to thepoint-of-sale terminal; verifying with the processor of the serviceprovider system that the payment is in accordance with the transactioninstructions; and updating with the processor of the service providersystem the transaction-specific page to display a transaction receiptconfirming the payment at the point-of-sale.
 24. The method of claim 23,further comprising notifying with the communicators interface of theservice provider system the merchant that the consumer has provided thepayment.
 25. The method of claim 23, wherein the token ID is in a formselected from the group consisting of: a barcode, a pin number, and aquick response (QR) code.
 26. The method of claim 25, further comprisingreceiving with the processor of the service provider system theconsumer's selection of the point-of-sale terminal on the web-basedinterface and selecting with the processor of the service providersystem the form of the token ID based on the point-of-sale terminal. 27.The method of claim 23, further comprising: receiving with thecommunications interface of the service provider system geolocationinformation from the consumer; identifying with the processor of theservice provider system the point-of-sale based on the geolocationinformation; and updating with the processor of the service providersystem the transaction-specific page to display the address of thepoint-of-sale.
 28. The method of claim 27, wherein the token ID is in aform selected from the group consisting of: a barcode, a pin number, anda quick response (QR) code.
 29. The method of claim 28, furthercomprising selecting with the processor of the service provider systemthe form of the token ID based on the point-of-sale terminal.
 30. Amethod for facilitating a payment between ma online merchant and aconsumer, wherein the consumer provides a payment request through amobile application on a mobile device for payment at a point-of-saleterminal that is local to the consumer and remote to the merchant, themethod comprising: receiving with a communications interface of aservice provider system the payment request made through the mobileapplication on the mobile device; generating with a processor of theservice provider system transaction instructions for the paymentrequest; receiving with the communications interface of the serviceprovider system the consumer's contact information; linking with theprocessor of the service provider system the consumer's contactinformation to the transaction instructions; creating with the processorof the service provider system transaction-specific page instructionsfor the mobile application; transmitting with the communicationsinterface of the service provider system the transaction-specific pageinstructions to the consumer at the consumer's contact information;updating with the processor of the service provider system thetransaction-specific page instructions to cause the mobile device todisplay instructions to the consumer on bow to provide the payment forthe purchase request at the point-of-sale terminal; generating with theprocessor of the service provider system a token ID; linking with theprocessor of the service provider system the token ID to the transactioninstructions; updating with the processor of the service provider systemthe transaction-specific page instructions to cause the mobile device todisplay the token ID; receiving with the communications interface of theservice provider system confirmation that the consumer presented thetoken ID and the payment to the point-of-sale terminal; verifying withthe processor of the service provider system that the payment is inaccordance with the transaction instructions; and updating with theprocessor of the service provider system the transaction-specific pageinstructions to cause the mobile device to display a transaction receiptconfirming the payment at the point-of-sale.
 31. The method of claim 30,further comprising notifying with the communications interface of theservice provider system the merchant that the consumer has provided thepayment.
 32. The method of claim 30, wherein the token ID is in a formselected from the group consisting of: a barcode, a pin number, and aquick response (QR) code.
 33. The method of claim 32, further comprisingselecting with the processor of the service provider system the form ofthe token ID based on the point-of-sale terminal.
 34. The method ofclaim 30, further comprising: receiving with the communicationsinterface of the service provider system geolocation information fromthe mobile device; identifying with the processor of the serviceprovider system the point-of-sale based on the geolocation information;and updating with the processor of the service provider system thetransaction-specific web page to display the address of thepoint-of-sale.
 35. The method of claim 34, wherein the token ID is in aform selected from the group consisting of: a barcode, a pin number, anda quick response (QR) code.
 36. The method of claim 35, furthercomprising selecting with the processor of the service provider systemthe form of the token ID bred on the point-of-sale terminal.
 37. Amethod for facilitating a payment between a consumer and a remote payee,wherein the consumer provides a payment request on a web-based interfaceto make the payment at a point-of-sale terminal that is local to theconsumer, the method comprising: receiving with a communicationsinterface of a service provider system the payment request made on theweb-based interface; generating with a processor of the service providersystem transaction instructions for the payment request; receiving withthe communications interface of the service provider system contactinformation for the consumer; linking with the processor of the serviceprovider system the contact information to the transaction instructions;causing with the processor of the service provider system the web-basedinterface to display of a portion of the transaction instructionsincluding how to provide the payment for the payment request at thepoint-of-sale terminal; generating with the processor of the serviceprovider system a token ID; linking with the processor of the serviceprovider system the token ID to the transaction instructions; causingwith the processor of the service provider system the web-basedinterface to display the token ID; receiving with the communicationsinterface of the service provider system confirmation that the consumerpresented the token ID and the payment to the point-of-sale terminal;verifying with the processor of the service provider system that thepayment is in accordance with the transaction instructions; and causingwith the processor of the service provider system the web-basedinterface to display a transaction receipt confirming the payment at thepoint-of-sale.
 38. The method of claim 37, further comprising notifyingwith the communication interface of the service provider system thepayee that the consumer has provided the payment.
 39. The method ofclaim 37, wherein the token ID is in a form selected from the groupconsisting of: a barcode, a pin number, and a quick response (QR) code.40. The method of claim 39, Author comprising receiving with theprocessor of the service provider system the consumer's selection of thepoint-of-sale terminal on the web-based interface and selecting with theprocessor of the service provider system the form of the token ID basedon the point-of-sale terminal.
 41. The method of claim 37, furthercomprising: receiving with the communications interface of the serviceprovider system geolocation information from the consumer; identifyingwith the processor of the service provider system the point-of-salebased on the geolocation information; and updating with the processor ofthe service provider system the transaction-specific page to display theaddress of the point-of-sale.
 42. A method for facilitating a paymentfrom a consumer to a remote payee, wherein the consumer provides apayment request though a mobile application on a mobile device forpayment at a point-of-sale terminal, the method comprising: receivingwith a communications interface of a service provider system the paymentrequest made through the mobile application on the mobile device;generating with a processor of the service provider system transactioninstructions for the payment request; receiving with the communicationsinterface of the service provider system the mobile device contactinformation; linking with the processor of the service provider systemthe mobile device contact information to the transaction instructions;crating with the processor of the service provider systemtransaction-specific page instructions for the mobile application;transmitting with the communications interface of the service providersystem the transaction-specific page instructions to the consumer at themobile device contact information; generating with the processor of theservice provider system a token ID; linking with the processor of theservice provider system the token ID to the transaction instructions;updating with the processor of the service provider system thetransaction-specific page instructions to cause the mobile device todisplay the token ID; receiving with the communications interface of theservice provider system confirmation that the consumer presented thetoken ID and the payment to the point-of-sale terminal; verifying withthe processor of the service provider system that the payment is inaccordance with the transaction instructions; and updating with theprocessor of the service provider system the transaction-specific pageinstructions to cause the mobile device to display a transaction receiptconfirming the payment at the point-of-sale.